Skip to content

Conversation

lgayard-brex
Copy link
Contributor

Bump org.apache.xmlbeans:xmlbeans from 3.0.1 to 5.3.0
Bump org.mozilla:rhino to 1.8.0, as fix to scripting module

  • Introduces org.mozilla:rhino-xml, from more recent 1.8.0

Fix scripting module compatibility with XMLBeans 5.3.0

  • Updates JSOMElementConvertor to handle XMLBeans 5.3.0 API changes
  • Adds fallback mechanisms for getXmlObject() method removal

dependabot bot and others added 3 commits August 14, 2025 18:07
- Update JSOMElementConvertor to handle XMLBeans 5.3.0 API changes
- Add fallback mechanisms for getXmlObject() method removal
- Implement string-based XML parsing as ultimate fallback
- Normalize XML whitespace to fix test assertions
- Maintain backward compatibility with older XMLBeans versions
@lgayard-brex lgayard-brex mentioned this pull request Aug 14, 2025
@cortlepp
Copy link
Member

Hey, thank you for looking into this! It seems like some code in xmlbeans-codegen still relies on the old xmlbeans version.

https://github.com/apache/axis-axis2-java-core/actions/runs/16973699000/job/48160085813?pr=980

- xmlbeans no longer supports the GENERATE_JAVA_VERSION attribute, i.e. the constant still exists but is not referenced and there is no way to set it with the new API
@cortlepp
Copy link
Member

Hey, thank you for looking into this! It seems like some code in xmlbeans-codegen still relies on the old xmlbeans version.

https://github.com/apache/axis-axis2-java-core/actions/runs/16973699000/job/48160085813?pr=980

I just noticed that I had already fixed at least some of those errors in my PR. I pushed them now (i hope you don't mind), we'll see if CI passes now.

@lgayard-brex lgayard-brex requested a review from cortlepp August 21, 2025 13:10
@lgayard-brex
Copy link
Contributor Author

Hey, thank you for looking into this! It seems like some code in xmlbeans-codegen still relies on the old xmlbeans version.
https://github.com/apache/axis-axis2-java-core/actions/runs/16973699000/job/48160085813?pr=980

I just noticed that I had already fixed at least some of those errors in my PR. I pushed them now (i hope you don't mind), we'll see if CI passes now.

Thank you for that. Hopefully, we're closer to getting this PR merged.

…MLString

Removes field scope from class JSOMElementConvertor. This field was created within an enter/exit block in the constructor, but after the exit block, its state was invalid.

Reduces try/catch scope when parsing xml object.
Copy link
Member

@cortlepp cortlepp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To me this looks good, but because I don't have any experience with / knowledge of xmlbeans all I can really do is a formal review(besides making sure that the tests pass).Since this library hasn't been updated in a while, and the API is not exactly foolproof to use, I'd guess that the chance of breaking things is quite high (but doing the update is unavoidable).

@robertlazarski from your point of view is there anything left to do here before we can merge this?

@robertlazarski
Copy link
Contributor

@cortlepp I no longer use XMLBeans at my day job as we use JSON with Axis2 now - anyways, in the early days of Axis2 I wrote some of the XMLBean docs and I know enough to test it via those docs as a basic sanity check.

Go ahead and merge it - I will do some basic tests after that.

@cortlepp cortlepp merged commit cb44227 into apache:master Aug 21, 2025
4 checks passed
@lgayard-brex lgayard-brex deleted the lgayard/xmlbeans-5.3.0 branch August 21, 2025 17:01
@lgayard-brex
Copy link
Contributor Author

@cortlepp thanks for merging. Can you hint at the release schedule? When can we expect a version to hit the Maven repos?

@robertlazarski
Copy link
Contributor

No later than end of year we hope - we need another release to do a Rampart 2.0.0.

Top priority for now is Axis2/C since the Apache board of directors - they monitor all 300+ projects - has that project on their radar due to a long time without a release.

@cortlepp
Copy link
Member

@robertlazarski is there something else that you want to get into the next release? Or is it just the release process/vote etc. that will take some time?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants